Dynomotion

Group: DynoMotion Message: 4033 From: Albert Płatek Date: 2/22/2012
Subject: Trajectory Planner Bug 2

Hi Tom,
Thank you for fast fix for "5milRadius" bug.
After copy and flash new firmware from (http://dynomotion.com/Software/Patch/Fix5milRaduis/DSPKFLOP.out), everything seemed to be ok, but not for long.

Motors stall, capture of acceleration show crazy numbers. It is repeatable error.
It seem that it happen on "Facet Angle" below 0.7
 
Please execute file in attachment with settings like in screenshot attached.
 
Btw. I can use "Facet Angle" of 1.0, it is ok, but can I be sure that this error won't happen again?
 
Best Regards
Albert Płatek
   @@attachment@@
Group: DynoMotion Message: 4060 From: Tom Kerekes Date: 2/22/2012
Subject: Re: Trajectory Planner Bug 2 [2 Attachments]
Hi Albert,
 
You discovered another Trajectory Planner bug.  (how many is that now ?).    It was more related to a specific combination of multiple segments than a small facet size.  It isn't easy to describe but basically during the optimization process the TP was able to look at 3 segments and logically deduce that a high velocity could be used on the middle segment, but then in a special case forgot to fully optimized the neighbor segment which resulted in a discontinuous velocity and a negative time.  The neighbor segments will now be optimized fully.
 
Please copy this DLL which contains the TP to your KMotion429\KMotion\Release directory to see if it resolves the issue.
 
 
Thanks
TK
 

Group: DynoMotion Message: 4062 From: Albert Date: 2/23/2012
Subject: Re: Trajectory Planner Bug 2
Hi Tom,
Thank you for fixing all bugs. It was propably
last bug in TP.
All day I was machining on cnc router many
different gcode programs without any
problems. In my opinion TP works perfect now :)
Thank you again Tom for your time and help.

Best Regards
Albert Platek



Dnia 2012-02-23 o godz. 08:03 Tom Kerekes <tk@...> napisał(a):

 

Hi Albert,
 
You discovered another Trajectory Planner bug.  (how many is that now ?).    It was more related to a specific combination of multiple segments than a small facet size.  It isn't easy to describe but basically during the optimization process the TP was able to look at 3 segments and logically deduce that a high velocity could be used on the middle segment, but then in a special case forgot to fully optimized the neighbor segment which resulted in a discontinuous velocity and a negative time.  The neighbor segments will now be optimized fully.
 
Please copy this DLL which contains the TP to your KMotion429\KMotion\Release directory to see if it resolves the issue.
 
 
Thanks
TK